 |
|
|
 |
| Subject: IMAP Semaphore Timeouts |
 |
 |
 |
| Product Area: Domino Server |
 |
| Technical Area: Functionality |
 |
| Platform: Solaris |
 |
| Release: 8.0.1 |
 |
| Reproducible: Not attempted |
 |
 |
 |
 |
We have a segment of our business that are heavy imap users. There are roughly 3600 imap accounts distributed across two separate domino servers. Frequently, in fact sometimes daily, the IMAP process on these dominos will stop responding. If you look at the console and sh tasks, you'll see the server providing service for several accounts over IMAP, however it will not allow any new logins to succeed. Sometimes, you can restart the imap task to resolve the issue, other times that won't complete and a server restart becomes necessary. Through an effort with IBM Support, after implementing IMAP debugging and semaphore debugging, it was determined that there is a semaphore timeout in the IMAP process and they've created an internal SPR to investigate futher. However, after the IMAP debugging was put in place, error messages like this run rampant throughout the console:
[23486:00176-00020] 02/26/2009 20:46:33.52 IMAP CITask SendErrorHandler> ERROR: (XXX.XXX.XXX.XXX) Send failed (did not timeout), error = 0A02h (Remote system no longer responding)
[23486:00176-00020] 02/26/2009 20:46:33.52 IMAP CITask SendErrorHandler> Running default handler, error = 0A02h (Remote system no longer responding)
Where XXX.XXX.XXX.XXX is the ip address of one of our sendmail imap proxies.
Any inclination of what would cause an error like this from IMAP? Is this contributing to our IMAP problems in general?
Any ideas or suggestions are greatly appreciated.
 
Feedback number WEBB7PNJK6 created by ~Arnold Asanikonylen on 02/27/2009
|
| |
|
Return to top
Printer-friendly
